src/pages/ContributorProfile/ContributorProfile.tsx (1)

33-37: ⚠️ Potential issue | 🔴 Critical | ⚡ Quick win

Critical: Missing error handling for PR search will cause runtime crash.

The PR search endpoint can also return GitHub API error responses (e.g., rate limits, invalid queries), but unlike the user fetch, there's no error check here. If prsData.items is undefined (because the response was an error object), line 79 will crash with TypeError: Cannot read property 'length' of undefined.

🐛 Proposed fix

 const prsRes = await fetch(
   `https://api.github.com/search/issues?q=author:${username}+type:pr`
 );
 const prsData = await prsRes.json();
+if (prsData.message) throw new Error(prsData.message);
 setPRs(prsData.items);

Or, applying the same HTTP status check pattern:

 const prsRes = await fetch(
   `https://api.github.com/search/issues?q=author:${username}+type:pr`
 );
+if (!prsRes.ok) {
+  throw new Error(`GitHub API error: ${prsRes.status} ${prsRes.statusText}`);
+}
 const prsData = await prsRes.json();
 setPRs(prsData.items);

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/pages/ContributorProfile/ContributorProfile.tsx` around lines 33 - 37,
The PR search fetch in ContributorProfile (variables prsRes, prsData, setPRs and
the template using username) is missing HTTP/error handling; update the PR fetch
to check prsRes.ok (or status) before reading prsData, and if the response is
not ok or prsData.items is undefined, log or surface the error and call
setPRs([]) (or a safe fallback) instead of using prsData.items directly so
subsequent code doesn't crash when items is missing. Ensure you reuse the same
error-check pattern used for the user fetch: await prsRes.json(), verify
prsRes.ok, handle non-OK responses (including rate limit/error objects) and set
a safe empty array via setPRs when necessary.